Use async singleton router for MemoryRouterProvider #114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are using the
next-router-mock/async
provider and had a bunch of issues with the Provider, as it appeared all manipulations of the router get ignored by our components.Looking into the code, I discovered why: The
<MemoryRouterProvider />
ignores theasync
prop unless anurl
is given. However, when anurl
is given, a new router is created.This should return the async singleton when requested - however, I could not test if it works for our application as I couldn't figure out how to include the package without it being published.